Device Scout system requirements

Device Scout is installed on a Windows server that can reach your printers. Use these requirements to choose and size the server, and to open the right network ports.

Supported operating systems

Windows Server 2025, 2022, 2019 and 2016, and Windows 11 and Windows 10, 32-bit and 64-bit. Use a server operating system in production.

You can install only one Device Scout on each operating system. To scan several network segments with separate Device Scouts, install each one on its own virtual machine.

Server sizing

Size the server by how many IP addresses it scans and how many printers it manages. CPU figures are for single-core CPUs, and a multi-core CPU counts as several: for example, a dual-core 1.2 GHz CPU meets a requirement for 2 x 1.2 GHz.

Size	Scan size	Printers	CPU	RAM	Free disk space	Network
Small	Up to 5,000 IP addresses	Up to 500	2 x 1.2 GHz or faster (32-bit or 64-bit)	2 GB	20 GB	100 Mbps
Medium	5,000 to 10,000 IP addresses	500 to 1,000	2 x 1.2 GHz or faster (32-bit or 64-bit)	4 GB	20 GB	100 Mbps
Large	10,000 to 20,000 IP addresses	1,000 to 2,000	2 x 1.2 GHz or faster (64-bit)	4 GB	40 GB	1,000 Mbps
Larger	Over 20,000 IP addresses	Over 2,000	Contact HP Development Company, L.P.

Virtual machines: these figures are for physical hardware. Convert them to virtual resources using your virtualization platform's guidelines.
Other discovery tools on the same server: add these requirements to theirs.

Software and access

Requirement	Details
.NET Framework	Microsoft .NET Framework 4.7.2 or later. It's installed automatically if it's missing, and it can run alongside other .NET versions.
TLS	TLS 1.2 must be turned on.
Administrator access	You need administrator rights on the server to install Device Scout.
Domain	The server must be in the same Windows domain as users' computers when you install. With the Local Connector and Active Directory as the authentication provider, it must be joined to the same on-premises Active Directory domain as the computers running Print Scout.

Network

Device Scout needs to reach:

The HP Insights cloud APIs over 443 TCP (TLS 1.2), to upload printer data and download updates and settings.
Your printers, to collect printer data. With the Local Connector, it also secures integrated printers and authenticates users through them.

Also check that:

Secure printers can reach the Device Scout server's fully qualified domain name on port 4321.
The Windows Firewall rule for Device Scout is applied.
If the server reaches the internet through a proxy server, you have its address, port, and any username and password. See Use the Device Scout Configuration tool.

Ports for integrated printers

Outbound means from Device Scout to the printer. Inbound means from the printer to Device Scout.

Manufacturer	Direction	Port	Protocol
HP	Outbound	443 TCP	TLS 1.2
HP	Outbound	7627 TCP	TLS 1.2
HP	Outbound	161 UDP	SNMP
HP	Inbound	4321 TCP	TLS 1.2
Konica Minolta	Outbound	80 TCP	HTTP
Konica Minolta	Outbound	50003 TCP	TLS 1.2
Konica Minolta	Outbound	161 UDP	SNMP
Konica Minolta	Inbound	4321, 50004 and 50006 TCP	TLS 1.2
Lexmark	Outbound	443 TCP	HTTP
Lexmark	Outbound	161 UDP	SNMP
Lexmark	Inbound	4321 TCP	TLS 1.2
Ricoh	Outbound	443 TCP	TLS 1.2
Ricoh	Outbound	51443 TCP	TLS 1.2
Ricoh	Outbound	161 UDP	SNMP
Ricoh	Inbound	4321 TCP	TLS 1.2
Xerox	Outbound	443 TCP	HTTP
Xerox	Outbound	161 UDP	SNMP
Xerox	Inbound	4321 TCP	TLS 1.2
Canon	Outbound	8443 TCP
Toshiba	Outbound	49630 and 50083 TCP

Antivirus and endpoint protection

Your antivirus or endpoint protection software must trust the .exe and .dll files in these folders and their subfolders, and the Windows services for Device Scout and the Local Connector:

Folders	Windows services
C:\Program Files (x86)\HP\DeviceScout C:\Program Files (x86)\HP\HP Secure Print Service	HP Device Scout Service HP Secure Print Service